Methods and apparatus for registering a device to server

ABSTRACT

A method for registering a device in a server is provided. The method includes connecting a first device positioned in a certain area to a server; and registering a second device by transmitting identification information of the second device positioned in the certain area to the server by the first device, and storing the identification information of the second device in the server.

PRIORITY

This application claims priority under 35 U.S.C. § 119(a) to KoreanPatent Application No. 10-2011-0100121, which was filed in the KoreanIntellectual Property Office on Sep. 30, 2011, the entire disclosure ofwhich is incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to a method and apparatus forregistering a device in a server, and more particularly, to a method andapparatus for registering devices positioned in the same network in aserver.

2. Description of the Related Art

Various devices are currently being used in the home, which include, forexample, an information device such as a Personal Computer (PC), acommunication device such as a phone, a broadcast device such as aTelevision (TV), and Audio and Video (AV) devices such as a DigitalVideo Disc (DVD) player and a digital camera. Home automation forautomatically controlling these devices has already entered themarketplace.

Home automation first separately controlled the devices using a phone orinfrared rays. Specifically, early home automation did not involve aconnection between the individual devices. However, through thedevelopment of communication technologies, a method of establishing anetwork between home appliances, which utilizes a controller forcontrolling the network, is has been used for integral management.

A system for integrally managing home appliances by establishing anetwork for the appliances is referred to as a “home network system”.The home network system connects various network home appliances (e.g.,a TV, a washing machine, a microwave oven, a gas range, an audio player,an air conditioner, and a boiler, etc.), lighting, a gas valve, and afront door, etc. to a controller such as a home gateway and a homeserver, and controls the connected devices through a certain terminal(e.g., a remote controller).

Various devices are being introduced that have applied technologies forefficiently implementing data sharing between devices, which is requiredin providing a home network service or an integrated service ofcommunication and broadcasting.

The Digital Living Network Alliance (DLNA) is an official partner forhome network commercialization, and is a new name of Digital HomeWorking Group (DHWG), which was launched in June, 2003.

The goal of the DLNA is to establish a mutually compatible platformbased on the already established and publicized industry standards andto realize convergence between industries. The DLNA is promoting theintroduction of guidelines for companies based on the Universal Plug andPlay (UPnP), which is widely used in companies that manufacture homeappliances, personal computers, and wireless devices, etc.

The UPnP is a technology that allows communication between home devicesconnected to the network without a complicated setting procedure, andallows a device to automatically find a service held by another device.

Further, the guidelines, which are currently being introduced in theDLNA, provides a design principal allowing contents to be shared betweendifferent brands and products through the wired/wireless home networkbetween home appliances, personal computers and wireless devices. Hence,the products, which are designed according to the guidelines, can sharemedia contents such as music, pictures and video files, through the homenetwork.

When sharing contents between devices in the DLNA-based home networkenvironment, the home network data sharing system controls services inconsideration of the characteristics of the devices and thecommunication environment. The home network data sharing system alsoallows interworking with various servers in the communication network inorder to provide better quality services. When registration to theservice is necessary for interworking with a server, registration isperformed for each device.

SUMMARY OF THE INVENTION

The present invention has been made to address at least the aboveproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the present inventionprovides a technology for registering a device in a server through oneof a plurality of devices in a home network.

Another aspect of the present invention provides a technology forregistering another device in another home network in a server through adevice in a home network, in another home network that is different froma home network positioned in the same server.

In accordance with an aspect of the present invention, a method isprovided for registering a device in a server. A first device isconnected to the server. A second device is registered with the serverby transmitting identification information of the second device from thefirst device to the server, and storing the identification informationof the second device in the server. The first device and the seconddevice are disposed within at least one network connected to the server.

In accordance with another aspect of the present invention, a method isprovided for registering a device in a server. Identificationinformation of a second device is received at the server from a firstdevice. The second device is registered with the server by storing thereceived identification information of the second device. The firstdevice and the second device are disposed within at least one networkconnected to the server.

In accordance with an additional aspect of the present invention, adevice is provided that includes a communication unit. The device alsoincludes a controller that connects the communication unit to a server,and transmits identification information of another device to the serverthrough the communication unit so that the other device is registered inthe server. The first device and the second device are disposed withinat least one network connected to the server.

In accordance with a further aspect of the present invention, a serveris provided for registering a device. The server includes a storage unitand a communication unit that communicates with a first device. Theserver also includes a controller that receives identificationinformation of a second device from the first device, stores thereceived identification information in the storage unit, and registersthe second device with the server. The first device and the seconddevice are disposed within at least one network connected to the server.

In accordance with another aspect of the present invention, a system isprovided for registering a device. The system includes a first device,and a second device in communication with the first device. The systemalso includes a server that receives identification information of thesecond device from the first device, stores the received identificationinformation, and controls registration of the second device. The firstdevice and the second device are disposed within at least one networkconnected to the server.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of the presentinvention will be more apparent from the following detailed descriptionwhen taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a diagram illustrating the connection of a plurality of homenetworks to a server, according to an embodiment of the presentinvention;

FIG. 2 is a circuit diagram illustrating a device, according to anembodiment of the present invention;

FIG. 3 is a procedural diagram illustrating a process of registeringanother device in a server using one of devices in a home network,according to an embodiment of the present invention;

FIG. 4 illustrates icons for executing applications in a display,according to an embodiment of the present invention;

FIG. 5 illustrates contents in a first device and device management menuicons in a display of a display unit, according to an embodiment of thepresent invention;

FIG. 6 illustrates a display when a device in a home network can befound, according to an embodiment of the present invention;

FIG. 7 illustrates a list of devices in a home network, according to anembodiment of the present invention;

FIG. 8 illustrates a state in which a selected device is registered in aserver, according to an embodiment of the present invention;

FIG. 9 illustrates a state of an additionally registered device and acontents list of the registered device, according to an embodiment ofthe present invention;

FIG. 10 illustrates correspondence in a first device according to aresponse that is set in a second device when registering the seconddevice in a server, according to an embodiment of the present invention;

FIG. 11 illustrates the selection of the use of an already registereddevice account or the creation of a new account of the first device,according to an embodiment of the present invention;

FIG. 12 is a procedural diagram illustrating a process in which a seconddevice requests a password from a first device when the first deviceconnects to the second device, according to an embodiment of the presentinvention;

FIG. 13 illustrates a list of the second device in the display of thefirst device, according to an embodiment of the present invention;

FIG. 14 illustrates a password input window in a display of a firstdevice, according to an embodiment of the present invention;

FIG. 15 illustrates a state in which a second device is registered in aserver through a first device, according to an embodiment of the presentinvention;

FIG. 16 illustrates the registering of a third device in another homenetwork in a server through a first device, according to an embodimentof the present invention;

FIG. 17 is a procedural diagram illustrating a process in which anotherdevice in another home network is registered in a server using one ofthe devices in different home networks, according to an embodiment ofthe present invention;

FIG. 18 illustrates a search icon for finding devices in a first homenetwork and a second home network in a display of a first device,according to an embodiment of the present invention;

FIG. 19 illustrates a list of other devices in a first home network anda list of other devices in a second home network, according to anembodiment of the present invention;

FIG. 20 illustrates lists of other devices in a second home network in adisplay of the first device, according to an embodiment of the presentinvention;

FIG. 21 is a flowchart illustrating a process of registering anotherdevice in a server using one of devices in a home network, according toan embodiment of the present invention;

FIG. 22 is a flowchart illustrating a process in which a second devicerequests a password from a first device when the first device connectsto the second device, according to an embodiment of the presentinvention; and

FIG. 23 is a flowchart illustrating a process in which another device inanother home network is registered in a server using one of the devicesin different home networks, according to an embodiment of the presentinvention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION

Embodiments of the present invention are described in detail withreference to the accompanying drawings. The same or similar referencenumbers may be used throughout the drawings to refer to the same or likecomponents. Detailed descriptions of constructions or processes wellknown in the art may be omitted to avoid obscuring the subject matter ofthe present invention.

According to an embodiment of the present invention, in a certainnetwork environment where various electronic devices are connected toone device management unit based on an Internet Protocol (IP), thecontrol of a plurality of electronic devices can be supported. In anembodiment of the present invention, the certain network environment canbe represented as a network environment where a plurality of electronicdevices are constituted within a certain area, such as, for example, ahouse, an office, a hospital, or a factory.

In embodiments of the present invention, the certain area can representa home network, an in-house network, an in-building network, a networkconnecting buildings, or a plurality of home networks that are connectedto the same server.

FIG. 1 is a diagram illustrating the connection of a plurality of homenetworks to a server, according to an embodiment of the presentinvention.

FIG. 1 is a diagram representing an entire system in which a device isregistered in a server. The system includes a server 110, a first homenetwork 120, and a second home network 150.

The server 110 is connected to the first home network 120 and the secondhome network 150, and each home network 120 and 150 includes differentdevices.

Because the server 110 is connected to the home networks 120 and 150,the server 110 can allow each of the devices to be connected to theserver 110.

A first device 130 or a second device 140, which are different from eachother, can be connected to the first home network 120. A third device130 or a fourth device 170, which are different from each other and thedevices connected to the first home network 120, can be connected to thesecond home network 150.

The UPnP can be used for communication between the first device 130 andthe second device 140 in the first home network 120, and the UPnP can beused for communication between the third device 160 and the fourthdevice 170 in the second home network 150.

Further, the UPnP can be used for communication between the first homenetwork 120 and the second home network 150.

FIG. 2 illustrates a circuit diagram of a device, according to anembodiment of the present invention.

Referring to FIG. 2, a device 200 includes a storage unit 210, a displayunit 220, a controller 230 and a communication unit 240.

The storage unit 210 stores a password, an ID, or identificationinformation of the device 200. The identification information includesinformation that can identify the device 200, such as a unique number, aproduct name and a serial number, etc.

The display unit 220 displays an interface screen between the device 200and the server (e.g., the server 110 of FIG. 1).

The controller 230 can control the device 200 to be registered in theserver. Further, the controller 230 can control another device to beregistered in the server through the device 200.

Further, the controller 230 controls the connection between devices inthe home network based on the UPnP. The communication unit 240 connectsthe device 200 to another device, the home network or the server.

FIG. 3 is a procedural diagram illustrating a process of registeringanother device in a server using one of the devices in a home network,according to an embodiment of the present invention.

Referring to FIG. 3, a first device 310 executes an application forconnecting to a server 330, and a user inputs an Identifier (ID) and apassword, step 311. In accordance with another embodiment of the presentinvention, the ID and the password can be stored in advance and can besent to the server by the executed application.

The server 330 checks the inputted ID and password, and if the inputtedID and password coincide with the registered ID and password, anapproval message is sent to the first device 310 so that the firstdevice 310 can communicate with the server 330, in step 331.

The first device 310 requests registration by sending identificationinformation of the first device 310 through the controller 230, in step312.

The identification information of the first device can be stored in thestorage unit 210.

The server 330 receives identification information of the first device,and allows registration of the first device 310. Further, the server 330sends a confirmation signal of the first registration to the firstdevice 310, in step 332.

After the first device 310 is registered in the server 330, the firstdevice 310 finds a second device 320 that exists in the home networkthrough the communication unit 240, in step 313.

Specifically, in step 321, the second device 320 repeatedly transmits amessage, which indicates the state of the second device 320, to thefirst device 310 at regular time intervals in the home network while inan idle mode, which is an unused state.

The first device 310 communicates with the second device 320 in the homenetwork using the received message, in step 313.

When the second device 320 sends the message to the first device 310,the second device 320 can be in the idle mode or in a wake-up mode,which is an in-use state.

The first device 310 receives the message through the controller 230,and asks the second device 320 if it has been registered in the server330, in step 314.

When the second device 320 is in the idle mode and the second device 320receives the inquiry about registration from the first device 310, thesecond device 320 is converted into the activated state, in step 322, sothat it can communicate with the first device.

The activated second device 320 transmits a message to the first device310 for server registration, in step 323.

The message can include the identification information of the seconddevice 320.

The first device 310 sends a request for registration of the seconddevice 320 to the server 330 based on the message received from thesecond device 320, in step 315.

The server 330 checks the received registration request, and registersthe second device 320, in step 333.

If the registration of the second device 320 is completed in the server330, the first device 310 completes the process of registering thesecond device in the server 330, in step 316, and the second devicecompletes the process of being registered in the server 330 through thefirst device 310, in step 324.

The server 330 can include a storage unit where the identificationinformation of the first device 310 and the identification informationof the second device 320 are stored, a communication unit thatcommunicates with the first device 310, and a controller that controlsregistration of the second device 320 based on the identificationinformation of the second device 320 that is provided through the firstdevice 310.

In FIG. 3, unlike server registration through each device, a device canbe registered in the server 330 through another device among a pluralityof devices in the home network.

For example, when a user has a plurality of devices, only one deviceamong the plurality of devices is registered in the server, and only oneaccount is formed in the server, the user can register other devicesthrough the established account.

The account can include device information and user information of thedevice.

The account can also include a plurality of devices because deviceinformation and user information of the other device can be added.

In order for the device to connect to the server, an ID and a passwordcan be inputted to the account of the device.

FIGS. 4 to 10 relate to the embodiment of the present inventiondescribed with respect to FIG. 3.

FIG. 4 illustrates icons for executing applications in a display,according to an embodiment of the present invention.

Referring to FIG. 4, an icon 420, which searches for the second device320, is displayed in a display 410 of the first device 310.

If the icon 420 is selected, a convergence application, which searchesfor the second device 320 in the home network, is executed.

FIG. 5 illustrates contents in a first device and device management menuicons in a display of a display unit, according to an embodiment of thepresent invention.

If the convergence application is executed and the first device 310 isalready registered in the server, the convergence application transmitsthe ID and password, the device is logged in at the server, and contents510 of the device are displayed in a display 540 through the displayunit 220.

When the first device 310 is not registered in the server and the icon420 in the display 540 of the first device 310 is selected, the ID andpassword for connection to the server are displayed in the display 540.

If the ID and password are inputted in the display 540, the display unit220 and the controller 230 transmit the ID and password obtained throughthe display unit 220 to the server.

The server checks the received ID and password and allows the connectionof the first device 310.

The connection indicates that the first device 310 connects to theserver.

A rectangular bar 511 shown in the display 540 indicates an amount ofeach of the contents that has been executed.

For example, if the rectangular bar 511 is long, all of the contentshave been executed, and if the rectangular bar 511 is short, only partof the contents have been executed. For example, when the contents are aone-hour movie, a user may watch only part of the movie. If the moviehas been played for 30 minutes, the rectangular bar 511 reaches themiddle.

In contrast, if the user finished watching the movie, the rectangularbar 511 reaches the end of the right edge.

If a registration icon 520 in the display is selected, the devicemanagement menu is executed.

The device management menu is an application that searches for devicesin the home network.

FIG. 6 illustrates a display in which a device in a home network can befound, according to an embodiment of the present invention.

In FIG. 6, if the registration icon 520 is selected, the screen of FIG.5 is converted into a screen that searches for another device in thehome network through the device.

An arrow bar 610 indicates that a display 630 is the device managementmenu.

The display 630 of FIG. 6 can include the arrow bar 610 indicating thestate of the display 630, and a search icon 620 that executes anapplication that searches for devices in the home network.

If the search icon 620 in the display 630 is selected, an applicationthat searches for another device in the home network through a device,can be executed.

The display unit 220, which controls the display 630, controls the arrowbar 610 or the search icon 620 displayed in the display 630.

FIG. 7 illustrates a list of devices in a home network shown in thedisplay when a search icon is selected, according to an embodiment ofthe present invention.

The controller 230 is positioned in the first device 310, and the firstdevice 310 and the second device exist in the same home network.

Hence, when a second device 720 is selected from a list 740 of aplurality of devices, the controller 230 can control the first device tocommunicate with the second device 720.

FIG. 8 illustrates the state where the selected device is registered ina server, according to an embodiment of the present invention.

Registration of the selected device 720 in the server is described indetail below. The selected device 702 represents the second device 810and 320.

The first device requests a message, which is necessary in registeringwith the server, to the second device 810, and the second device 810checks the request of the first device 310 and transmits the requestedmessage to the first device 310.

The message can represent the identification information of the seconddevice 810.

The first device 310 sends a request for registration of the seconddevice 810 to the server based on the received message of the seconddevice 810.

The server checks the registration request received from the firstdevice, and allows registration of the second device 810.

An arrow bar 830 indicates that the second device 810 is in a registeredstate 820 with the server.

FIG. 9 illustrates a state of an additionally registered device and acontents list of the registered device, according to an embodiment ofthe present invention.

If the second device 810 is selected, the contents in the second device810 can be shown as illustrated in FIG. 9.

An arrow bar 910 indicates that contents 920 shown in a display 930 arethe contents 920 in the second device 810.

A rectangular bar 940 indicates the amount of the contents 920 that havebeen executed.

Specifically, if all of the contents 920 are executed, the rectangularbar 940 is lengthened to the right edge of the display 930.

As another example, if half of the contents are executed, therectangular bar 940 is lengthened to the middle of the display 930.

Therefore, the amount of contents 920 executed can be known through thelength of the rectangular bar 940.

FIG. 10 illustrates correspondence in a first device according to aresponse that is set in a second device when registering the seconddevice in a server, according to an embodiment of the present invention.

Referring to FIG. 10, the first device finds the second device in thehome network and attempts to communicate with the second device, andrequests registration of the second device to the server as illustratedin FIG. 6.

When the first device connects to the second device, the setting forconnection with the first device is shown in the screen of the seconddevice.

When the second device is registered in the server through the firstdevice, the connection of the first device and the second device can bedifferently constituted according to the response setting value of thesecond device.

The connection constitution of the second device can be represented by asetting change frame 1010.

The setting change frame 1010 represents various methods for connectionof the first device when the first device connects to the second device.

There are change items 1020, 1030, 1040 and 1050 in the setting changeframe 1010, and one of the change items 1020, 1030, 1040 and 1050 can beselected according to the condition.

Always Accept 1020 indicates that registration of the second device isalways requested to the server. There is no need to ask whether thefirst device will request registration of the second device when thesecond device is registered in the server through the first device.

Always Ask 1030 indicates that the first device asks the second devicewhether to request registration with the server before the registrationprocess of the second device to the server through the first device isstarted.

In Always Ask 1030, a pop-up window, in which the first device requestsconnection of the second device, can be shown in the display of thesecond device when the first device connects to the second device.

A phrase, which indicates allowance or rejection of the first device,can be inputted in the pop-up window shown in the second device.

The first device can obtain the device information of the second device,i.e., the identification information of the second device, by connectingto the second device. Further, the first device can request registrationof the second device by sending the obtained identification informationto the server.

Always Reject 1040 indicates that the second device does not allowcommunication of the first device when the second device is registeredin the server through the first device.

When Always Reject 1040 is selected, the second device cannot beregistered in the server using the first device.

In Ask for Password 1050, when the second device is registered in theserver through the first device, the second device can ask the firstdevice the password, receive and check the password inputted through thescreen of the first device, and accept or reject connection of the firstdevice.

In Ask for Password 1050, a pop-up window, where a password can beinputted, can be displayed in the display of the first device when thefirst device connects to the second device.

The password inputted in the pop-up window is compared with a presetpassword, and when the two passwords are the same, the second deviceallows connection of the first device.

In contrast, when the password inputted in the pop-up window isdifferent from the preset password, the second device rejects connectionof the first device.

The first device can connect to the second device, and obtain the deviceinformation of the second device, i.e., the identification informationof the second device. Further, the first device can send theidentification information to the server, and request registration ofthe second device.

FIG. 11 illustrates the selection of the use of an already registereddevice account or the creation of a new account of the first device,according to an embodiment of the present invention.

The display of FIG. 11 can be provided between the displays of FIGS. 4and 5 or between the displays of FIGS. 5 and 6. The first device canconnect to the server using an existing account 1110 of the first devicethat is already registered in the server, or can create a new account1120 of the first device and connect to the server.

The existing account 1110 indicates that the first device is registeredin the server.

The first device can connect to the server when the ID and password areinputted at the first device using the existing account 1110.

The server checks the received ID and password and allows for connectionof the first device.

The new account 1120 indicates that the first device is not registeredin the server.

The first device can request registration of the first device in theserver by sending the identification information of the first device tothe server.

If the server allows registration of the first device, the ID andpassword are inputted in the first device in order to make the accountof the first device in the server.

The first device sends the inputted ID and password to the server sothat the ID and password are stored in the server.

The ID and the password inputted in the display of the first device arecontrolled in the controller 230 and the display unit 220, and the IDand the password are stored in the storage unit 210.

When the first device connects to the server, the server asks the firstdevice for the ID and password stored in the server.

The first device shows the received inquiry from the server in a pop-upwindow.

The ID and the password inputted in the pop-up window are sent to theserver, and the server compares the ID and the password with the storedID and the password.

When the ID and the password are the same as the stored ID and password,the server allows connection of the first device.

FIG. 12 is a procedural diagram illustrating a process in which a seconddevice requests a password from a first device when the first deviceconnects to the second device, according to an embodiment of the presentinvention.

FIG. 12 illustrates a detailed procedural diagram for a password request1050 of FIG. 10.

FIG. 12 provides steps that are similar to those of FIG. 3, and furtherincludes requesting the password in step 1220, inputting the password instep 1230 and checking the password in step 1240.

A first device 1201 receives a message from a second device 1202, andasks the second device 1202 its state of registration in the server, instep 1210.

When the second device 1202 is in an idle state, the second device 1202is converted into the activated state.

The activated second device 1202 sends a request for the password to thefirst device 1201, in step 1220.

The first device 1201, which has received the password request, displaysa pop-up window, where the password can be inputted, in the display ofthe first device 1201.

The first device 1201 transmits the inputted password to the seconddevice 1202, in step 1230, and the second device 1202 receives thetransmitted password and examines whether the received password is thesame as the password which has been already set, in step 1240.

The set password can be a password that has been already stored in thesecond device 1202.

When the received password coincides with the stored password, thesecond device 1202 transmits the message of the second device 1202,which is necessary in registering with the server 1203, to the firstdevice 1201.

The message can be the identification information of the second device1202.

The first device 1201 sends a request for registration of the seconddevice 1202 to the server 1303 using the received message of the seconddevice 1202.

The server 1303 receives the registration request of the second device1202 from the first device 1201, and allows registration of the seconddevice 1202 by checking the message of the second device 1202 receivedfrom the first device 1201.

FIGS. 13 to 15 relate to the embodiment of the present inventiondescribed with respect to FIG. 12.

FIG. 13 illustrates a list in the display of the first device, accordingto an embodiment of the present invention.

FIG. 13 shows a list 1303 of devices in the home network in a display1301 of the first device that is provided when the search icon 620 isselected.

If a second device 1302 is selected from the list 1303 of devices shownin the first device 1201, the first device 1201 registers the seconddevice 1302 with the server.

FIG. 14 illustrates a password input window in a display of a firstdevice, according to an embodiment of the present invention.

When the first device 1201 connects to the second device 1202, thesecond device 1202 can send a request for the password to the firstdevice 1201 in order to restrict connection of the first device 1201, instep 1050.

If the second device 1202 requests the password, a password input window1402 is displayed on display 1401 of the first device 1201.

If a password 1403 is inputted into the password input window 1402 and aconfirmation icon 1404 is selected, the display unit 220 transmits theinputted password to the controller 230.

When the password is compared with the preset password and the passwordis the same as the preset password, the controller 230 controls thefirst device 1201 to connect to the second device 1202.

FIG. 15 illustrates a state in which a first device registers a seconddevice in a server, according to an embodiment of the present invention.

When the password received from the first device 1201 is compared withthe preset password and the two passwords are the same, the seconddevice 1202 transmits a message allowing for connection to the firstdevice 1201.

If the first device 1201 receives the allowance message from the seconddevice 1202, the first device 1201 sends a request for identificationinformation to the second device 1202.

The second device 1202 checks the request of the first device 1201, andtransmits the identification information of the second device to thefirst device 1201.

The first device 1201 obtains the identification information of thesecond device 1202, which is necessary for registration of the seconddevice 120 with the server 1203.

The first device 1201 requests registration of the second device 1202 bytransmitting the identification information of the second device 1202 tothe server 1203.

The server 1203 checks an identification number of the second device1202, and allows registration of the second device 1202.

An arrow bar 1510 indicates that the second device 1202 is in aregistered state 1530 with the server in a display 1520 of the firstdevice 1202.

FIG. 16 illustrates the registering of a third device in another homenetwork in a server through a first device, according to an embodimentof the present invention.

A server 1610 is connected to a first home network 1620 and a secondhome network 1630.

The first home network 1620 is connected to first and second devices1621 and 1622, and the first and second devices 1621 and 1622 cancommunicate with each other using the UPnP.

Similarly, the second home network 1630 is connected to third and fourthdevices 1631 and 1632, and the third and fourth devices 1631 and 1632can communicate with each other using the UPnP.

Further, the first home network 1620 and the second home network 1630,which are connected to the same server 1610, can communicate with eachother using the UPnP.

The first device 1621, which is connected to the first home network1620, can find the third device 1631 in the second home network 1630through the UPnP.

Because the first home network 1620 and the second home network 1630 areconstituted independently, the Internet Protocols (IPs) allocated to thefirst and second devices 1621 and 1622 by the first home network 1620and the IPs allocated to the third and fourth devices 1631 and 1632 bythe second home network 1630 are the same, and thus, the IPs cancollide.

When the same IP exists between the first home network 1620 and thesecond home network 1630, the devices having the same IP cannotcommunicate with each other.

In order to prevent collision between the IPs, the IPs of the first homenetwork 1620 and the IPs of the second home network 1630 should becompared to check whether they have the same IP.

The first home network 1620 transmits the IPs of the first home network1620 to the second home network 1630, and the second home network 1630compares the transmitted IPs with the IPs of the second home network1630.

Further, the first home network 1620 can ask the second home network1630 the IPs of the second home network 1630, and obtain data of the IPsof the second home network 1630.

The first home network 1620 can check whether there is the same IP bycomparing the obtained IPs of the second home network 1630 with the IPsof the first home network 1620.

When a same IP exists in the IPs of the first home network 1620 and theIPs of the second home network 1630, the address of the collided IP canbe changed.

Specifically, the collided IPs among the IPs of the devices 1621, 1622,1631 and 1632 is changed to another IP, and the device connected to thecollided IP can be reallocated to another IP.

FIG. 16 illustrates an embodiment of the present invention, and the IPs,which are in use in the first home network 1620 and the second homenetwork 1630, are compared with each other, and are changed to anaddress of the IP where a collision will not occur.

Further, the first home network 1620 and the second home network 1630communicate with each other using the UPnP, and the first device 1621can be connected to the third device 1631 in the second home network1430.

The first device 1621 can ask the third device 1631 the identificationinformation of the third device 1631, and can obtain the identificationinformation.

The first device 1621 can transmit the identification information of thethird device 1631 to the server 1610, and can request registration ofthe third device 1631 to the server 1610.

The server 1610 checks the registration request, and transmits amessage, allowing registration of the third device 1631, to at least oneof the first device 1621 and the third device 1631.

Referring to FIG. 16, when the first device 1621 in the first homenetwork 1620 is registered in the server 1610, the account of the firstdevice 1621 can be formed in the server 1610.

Further, the first device 1621 can register the third device 1631 inthis account. Hence, the account can include a plurality of devices.

FIG. 17 is a procedural diagram illustrating a process where anotherdevice in another home network is registered in a server using one ofthe devices in different home network, according to an embodiment of thepresent invention.

The process and steps of FIG. 17 is similar to that of FIG. 3, with theexception of steps 1704-1706, which are described in detail below.

When the first home network 1620 and the second home network 1630 areconnected with the same server 1610, and there are no identical IPsbetween the IPs of the first home network 1620 and the IPs of the secondhome network 1630, a first device 1701 in the first home network 1620can communicate with a third device 1702 in the second home network1630.

The IP address allocated to the first device 1701 in the first homenetwork 1620 is transmitted to the second home network 1630 before thefirst device 1701 communicates with the third device 1702, in step 1704.

Further, the IP address allocated to the third device 1702 in the secondhome network 1630 can be transmitted to the first home network 1620, instep 1704.

The IP address of the first home network 1620 transmitted to the secondhome network 1630 can be compared with the IP address allocated to thethird device 1702 in the second home network 1630.

When the IP address allocated to the first device 1701 is compared withthe IP allocated to the third device 1702 and the two IP addresses arethe same, at least one of the two IP addresses is changed, in step 1705.

Specifically, one of the same IP addresses can be reallocated to anotherIP address.

If the IP address allocated to the first device 1701 is different fromthe IP address allocated to the third device 1702, the IP addressesremain unchanged.

If the IP address allocated to the first device 1701 is different fromthe IP address allocated to the third device 1702, the first device 1701can communicate with the third device 1702, in step 1706.

The process after step 1706 is the same as that described above withrespect to FIG. 3.

FIGS. 18 to 20 relate to the embodiment of the present inventiondescribed with respect to FIG. 17.

FIG. 18 illustrates a search icon for finding devices in a first homenetwork and a second home network in a display of a first device,according to an embodiment of the present invention.

If a search icon 1802 in a display 1801 of the first device 1701 isselected, the first device 1701 obtains the list of devices in the firsthome network 1620 and the list of other devices in the second homenetwork 1630.

FIG. 19 illustrates a list of devices in a first home network and a listof other devices in a second home network, according to an embodiment ofthe present invention.

If an icon 1901 of the first home network 1620 is selected, a firstdevice 1902 and a second device 1903 connected to the first home network1620 are displayed in the display 1905 of the first device.

The first home network 1620 connects to the second home network 1630connected with the server 1703, and the icon 1901 indicating the firsthome network 1620 and an icon 1904 indicating the second home network1630 are displayed in a display 1905 of the first device 1701.

Referring to FIG. 19, the server 1703 includes the first home network1620 and the second home network 1630, and each home network 1620 and1630 includes devices.

Hence, each of the devices can communicate with each other.

FIG. 20 illustrates a list of devices in a second home network in adisplay of the first device, according to an embodiment of the presentinvention.

As illustrated in FIG. 17, when the IP addresses allocated in the firsthome network 1620 do not collide with the IP addresses allocated in thesecond home network 1630, a list of other devices 2002 and 2003 can bedisplayed in the display 1950 of the first device 1701.

Specifically, when an icon 2001 of the second home network 1630 isselected, the list of other devices 2002 and 2003 can be displayed inthe display 1905 of the first device 1701.

For example, if the third device 2002 shown in the display 1950 of thefirst device 1701 is selected, the first device 1701 can communicatewith the third device 1702 and obtain identification information fromthe third device 1702.

The first device 1701 transmits the obtained identification informationto the server 1703 to request that the third device 1702 be registeredin the server 1703.

The server 1703 can receive identification information of the thirddevice 1702 and allow registration of the third device 1702.

FIG. 21 is a flowchart illustrating a process of registering anotherdevice in a server using one of devices in a home network, according toan embodiment of the present invention.

Referring to FIG. 21, the first device 310 can connect to the serverusing an application, in step S2101.

If the first device 310 connects to the server 330, the server asks thefirst device 310 for an ID or a password.

For example, a pop-up window, where the ID or the password is inputted,can be activated in the display of the first device 310, and the ID orthe password can be inputted in the pop-up window.

The server 330 receives the inputted ID or password, and compares theinputted ID or password with the pre-stored ID or password. If the twoIDs or passwords are the same, the connection of the first device 310 isallowed.

The first device 310 requests registration of the first device 310 bytransmitting identification information of the first device 310 to theserver 330, and the server 330 receives the registration request andallows registration of the first device 310, in step S2102.

The second device 320 periodically transmits a signal indicating thesecond device 320.

The first device 310 and the second device 320 are positioned within acertain area, the first device 310 senses the signal of the seconddevice in step S2103, and communicates with the second device 320.

The first device 310 asks the second device 320 about registration ofthe second device 320 with the server 330, in step S2104.

When the second device 320 receives the inquiry request, the state ofthe second device 320 is changed from an inactivated state to anactivated state, in step S2105.

In the inactivated state, it is difficult for the second device 320 totransmit identification information of the second device 320 to thefirst device 310, and thus, the state is changed to the activated state.

The user of the second device 320, or the one having the authority touse the second device 320, can check the inquiry about the registrationand allow registration of the second device 320, in step S2106.

Further, the data of the first device 310 received from the first device310 is compared with the data already stored in the storage unit 210,and if the two sets of data are the same, the second device 320 cantransmit an answer to the inquiry about registration of the seconddevice 320 to the first device 310.

If the first device 310 receives data allowing registration of thesecond device 320 from the second device 320, the first device 310transmits identification information of the second device 320 to theserver 330, and inquires about registration of the second device 320, instep S2107.

The server receives the registration inquiry from the first device 310and allows registration of the second device 320, in step S2108.

More specifically, the server 330 compares identification information ofthe first device received from the first device 310 with identificationinformation of the first device stored in the storage unit 210, and ifthe two sets of information are the same, the server 330 allowsregistration of the second device 320.

The controller can control the registration process.

FIG. 22 is a flowchart illustrating a process in which a second devicerequests a password from a first device when the first device connectsto the second device, according to an embodiment of the presentinvention.

FIG. 22 includes steps that are similar to those of FIG. 21, with theexception of steps inquiring about a password and inputting thepassword.

Referring to the flowchart of FIG. 22, the first device 1201 can connectto the server 1203 through the application, in step S2201.

If the first device 1201 connects to the server 330, the server 330 asksthe first device 1201 about the ID or password.

For example, a pop-up window, where the ID or the password is inputted,is activated in the display of the first device 1201, and the ID or thepassword can be inputted in the pop-up window.

The server 1203 receives the inputted ID or password, and if theinputted ID or password coincides with the already stored ID orpassword, the server 1203 allows connection of the first device 1201.

The first device 1201 requests registration of the first device 310 bysending identification information of the first device 1201 to theserver 1203, and the server 1203 receives the registration request andallow registration of the first device 1201, in step S2202.

The second device 1202 periodically transmits a signal indicating thesecond device 1202.

The first device 1201 and the second device 1202 are located within acertain area, and the first device 1201 senses the signal of the seconddevice in step S2203, and communicates with the second device 1202.

The first device 1201 asks the second device 1202 about registration ofthe second device 1202 with the server 1203, in step S2204.

When the inquiry request is received, the state of the second device1202 is changed from an inactivate state to an activated state, in stepS2205.

In the inactivated state, it is difficult for the second device 1202 totransmit identification information of the second device 1202 to thefirst device 1201, and thus, the state of the second device 1202 ischanged to the activated state.

The second device 1202 asks the first device 1201 about the password instep S2206. A window, where the password can be inputted, is displayedin the display of the first device 1201.

A user can check the password request from the first device 1201 andinput the password in the window displayed in the display of the firstdevice.

If the password is inputted in the window and the transmission button isselected, the password is transmitted to the second device 1202, in stepS2207.

The second device checks the password and receives the registrationrequest of the first device 1201, in step S2208.

Further, if the password coincides with the password stored in thestorage unit 210, the second device 1202 receives the registrationrequest of the first device 1201.

A user of the second device 1202, or the one having the authority to usethe second device 1202, checks the registration inquiry and allowsregistration of the second device 1202.

Further, if the data of the first device 1201 received from the firstdevice 1201 is compared with the data already stored in the storage unit210 and the two sets of data are the same, the second device 1202transmits the answer to the registration inquiry of the first device1201 to the first device 1201, in step S2209.

If the first device receives data allowing registration of the seconddevice 1202 from the second device 1202, the first device 1201 transmitsidentification information of the second device 1202 to the server 1203and inquires about registration of the second device 1202, in stepS2210.

The server 1203 checks a registration inquiry received from the firstdevice 1201 and allows registration of the second device 1202, in stepS2211.

More specifically, the server 1203 compares the identificationinformation of the first device received from the first device 1201 withthe identification information of the first device stored in the storageunit 210, and if the two sets of information are the same, the server1203 allows registration of the second device 1202.

The controller 230 can control the registration process and the processof inquiring about the password.

FIG. 23 is a flowchart illustrating a process in which another device inanother home network is registered in a server using one of the devicesin different home networks, according to an embodiment of the presentinvention.

FIG. 23 provides steps that are similar to those of FIG. 21, with theexception of the step of comparing the IP allocated in the first homenetwork with the IP allocated in the second home network.

Referring to the flowchart of FIG. 23, the first device 1701 connects tothe server 1703 using an application, in step S2301.

If the first device 1701 connects to the server 1703, the server 1703asks the first device about the ID or the password.

For example, a pop-up window, where the ID or the password is inputted,is activated in the display of the first device 1701, and the ID or thepassword is inputted in the pop-up window.

The server 1703 receives the inputted ID or password, and if theinputted ID or password coincides with the already stored ID orpassword, the server 1703 allows connection of the first device 1701.

The first device 1701 requests registration of the first device 1701 bytransmitting identification information of the first device 1701 to theserver, and the server receives the registration request and allowsregistration of the first device 1701, in step S2302.

The IP address allocated in the first home network can be compared withthe IP address allocated in the second home network 1630, in step S2303.

The IP addresses are compared because it is possible for the first homenetwork 1620 and the second home network 1630 to be independentlyconstituted, and for each home network to allocate the same IP addressto devices.

In the independent constitution of the home network, the IP address ofthe first device 1621 connected to the first home network 1620 cancoincide with the IP address of the third device 1631 connected to thesecond home network 1630.

The IP addresses are compared with each other, and when the same IPaddress exists, one of the two addresses is reallocated to another IPaddress, in step S2304.

Through the reallocation process, the IP address allocated in the firsthome network 1620 is constituted to be different from the IP addressallocated in the second home network 1630.

Home networks are connected to the same server and devices cancommunicate with each other in the home network, and thus, the firstdevice 1701 detects and connects to the third device 1702, in stepS2305.

The first device 1701 asks the third device 1702 about registration ofthe third device 1702, in step S2306.

If the third device 1702 receives the inquiry request, the state of thethird device 1702 is changed from the inactivated state to the activatedstate, in step S2307.

In the inactivated state, it is difficult for the third device 1702 totransmit identification information of the third device 1702 to thefirst device 1701, and thus, the state of the third device 1702 ischanged to the activated state.

A user of the third device 1702, or one having the authority to use thethird device 1702, checks the registration inquiry and allows theregistration of the third device 1702.

Further, the third device 1702 compares the data of the first device1701 received from the first device 1701 with the data pre-stored in thestorage unit 210, and if the two sets of data are the same, the thirddevice 1702 transmits the answer to the registration inquiry of thefirst device 1701 to the first device 1701, in step S2308.

If the first device 1701 receives data allowing registration of thethird device 1702 from the third device 1703, the first device 1701transmits identification information of the third device 1702 to theserver 1703 and inquires about registration of the third device 1702, instep S2309.

The server 1703 receives the registration inquiry from the first device1701 and allows registration of the third device 1702, in step 2310.

More specifically, the server 1703 compares identification informationof the first device 1701 received from the first device 1701 withidentification information of the first device 1701 stored in thestorage unit 210, and if the two sets of information are the same, theserver 1703 allows registration of the third device 1702.

The controller 230 can control the registration process and the processof comparing IP addresses and reallocating IP addresses.

According to embodiments of the present invention, a device can beregistered in a server through another of a plurality of devicespositioned in a home network. Further, a device positioned in a firsthome network can be registered in the server through another devicepositioned in a second home network.

While the invention has been shown and described with reference tocertain embodiments thereof, it will be understood by those skilled inthe art that various changes in form and detail may be made thereinwithout departing from the spirit and scope of the invention as definedby the appended claims.

What is claimed is:
 1. A method for registering a device in a server,the method comprising the steps of: connecting a first device to theserver; sending a message related to registration of a second devicewith the server, from the first device to the second device; receivingdata indicating allowance of the registration at the first device fromthe second device; and in response to the allowance of the registrationof the second device with the server, registering the second device withthe server by transmitting identification information of the seconddevice from the first device to the server, and storing theidentification information of the second device in the server; whereinthe first device and the second device are disposed within at least onenetwork connected to the server.
 2. The method of claim 1, wherein theidentification information comprises at least one of a unique number ofthe second device, a product name of the second device, and a serialnumber of the second device.
 3. The method of claim 1, furthercomprising: searching for the second device in the at least one networkby the first device.
 4. The method of claim 1, further comprising:connecting the first device to the second device and activating thesecond device.
 5. The method of claim 1, further comprising: receivingan inquiry about a password at the first device from the second device,when the first device connects to the second device.
 6. The method ofclaim 1, further comprising: receiving the identification information ofthe second device at the first device from the second device.
 7. Themethod of claim 1, further comprising: receiving a setting that limits aconnection of the second device at the first device.
 8. The method ofclaim 1, further comprising: registering the first device in the server.9. The method of claim 8, further comprising: generating an account ofthe first device in the server after registration of the first device inthe server, and connecting a plurality of devices to the account. 10.The method of claim 1, further comprising: receiving an inquiry about apassword at the first device from the second device.
 11. The method ofclaim 10, further comprising: transmitting the password from the firstdevice to the second device.
 12. The method of claim 1, furthercomprising: comparing an IP address allocated to the first device withan IP address allocated to the second device.
 13. The method of claim12, wherein the second device is disposed in a home network that isdifferent from a home network of the first device.
 14. The method ofclaim 12, further comprising: changing at least one of the IP address ofthe first device and the IP address of the second device when the IPaddress of the first device is the same as the IP address of the seconddevice.
 15. A device comprising: a communication unit; and a controllerthat connects the communication unit to a server, sends a messagerelated to registration of another device with the server to the otherdevice, receives data indicating allowance of the registration from theother device, and, in response to the allowance of the registration ofthe other device with the server, transmits identification informationof the other device to the server through the communication unit so thatthe other device is registered in the server; wherein the device and theother device are disposed within at least one network connected to theserver.
 16. The device of claim 15, further comprising: a storage unitthat stores the identification information of the other device.
 17. Thedevice of claim 15, wherein the identification information comprises atleast one of a unique number of the other device, a product name of theother device, and a serial number of the other device.
 18. The device ofclaim 15, wherein the controller controls registration of the otherdevice in the server.
 19. The device of claim 15, wherein the controllercontrols reception of an inquiry about a password from the other devicewhen the device connects to the other device.
 20. The device of claim19, wherein the controller controls transmission of the password fromthe device to the other device.